Weaving With Statecharts

Separation of Concerns separates requirements such as synchronization and scheduling from the core functionality of the software system. These requirements are often referred to as crosscutting concerns. The implementation of such requirements is scattered throughout the software system, which results in the code-tangling problem Aspect Oriented Programming provides the user with the ability to modularize, and weave the representation of crosscutting concerns in order to maximize code reusability and solves the code-tangling problem. Using the Unified Modeling Language (UML) to model and inter-weave these crosscutting concerns is an area thast is getting more attension from researchers, and is the theme of this paper. In this paper we present a formal design methodology to model the system’s concerns based on aspect-orientation. We show how to model and interweave the different sub-models that represent different concerns using UML’s Statecharts and Class Diagrams. In Addition our initial study shows that our approach demonstrates the benefits for aspect-oriented modeling, like maintainability, reusability and trace-ability at the design phase as well as at the implementation phase of the development life cycle.